Augmenting the display of data in a tree format

ABSTRACT

The method includes identifying a tree data structure. The method includes identifying one or more features in the identified tree data structure, wherein the one or more features comprise at least one of: a node of the tree data structure, an object of the tree data structure, an array of the tree data structure, an object property of the tree data structure, and a root of the tree data structure. The method includes determining whether one of the one or more identified features matches a feature that initiates execution of a rule, wherein the rule defines augmentations to the tree data structure based upon one or more features in the tree data structure. The method includes augmenting the identified tree data structure based upon the determined one or more matches of the one or more identified features and the feature that initiates execution of the rule.

BACKGROUND

The present invention relates generally to data trees, and moreparticularly to augmenting data in tree formats.

In computer science, a data tree is a widely used abstract data type(ADT) or data structure implementing this ADT that simulates ahierarchical tree structure, with a root value and subtrees of children,represented as a set of linked nodes.

A tree data structure can be defined recursively (locally) as acollection of nodes (starting at a root node), where each node is a datastructure consisting of a value, together with a list of references tonodes (the “children”), with the constraints that no reference isduplicated, and none points to the root.

Alternatively, a data tree can be defined abstractly as a whole(globally) as an ordered tree with a value assigned to each node. Boththe recursive and whole data tree perspectives are useful because a treecan be analyzed mathematically as a whole, when actually represented asa data structure tree, and worked separately by node (rather than as alist of nodes and an adjacency list of edges between nodes, as one mayrepresent a digraph, for instance). For example, looking at a tree as awhole, one can talk about “the parent node” of a given node, but ingeneral as a data structure a given node only contains the list of thenode's children but does not contain a reference to the node's parent(if any).

SUMMARY

Embodiments of the present invention disclose a method, computer programproduct, and system for augmenting data tree structures. In oneembodiment, in accordance with the present invention, thecomputer-implemented method includes identifying, by one or morecomputer processors, a tree data structure. The method further includesidentifying, by one or more computer processors, one or more features inthe identified tree data structure, wherein the one or more featurescomprise at least one of: a node of the tree data structure, an objectof the tree data structure, an array of the tree data structure, anobject property of the tree data structure, and a root of the tree datastructure. The method further includes determining, by one or morecomputer processors, whether one of the one or more identified featuresmatches a feature that initiates execution of a rule, wherein the ruledefines augmentations to the tree data structure based upon one or morefeatures in the tree data structure. The method further includes inresponse to determining that one or more identified features match atfeature that initiates execution of a rule, augmenting, by one or morecomputer processors, the identified tree data structure based upon thedetermined one or more matches of the one or more identified featuresand the feature that initiates execution of the rule.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment, in accordance with an embodiment of the presentinvention;

FIG. 2 is a flowchart depicting operational steps of a program foraugmenting tree data structures within the distributed data processingenvironment of FIG. 1, in accordance with an embodiment of the presentinvention;

FIG. 3 depicts an expanded tree data structure without augmenting thetree data structure, in accordance with an embodiment of the presentinvention;

FIG. 4 depicts a collapsed tree data structure without augmenting thetree data structure, in accordance with an embodiment of the presentinvention;

FIG. 5 depicts a collapsed tree data structure that has been augmentedto display certain features while in a collapsed state, in accordancewith an embodiment of the present invention; and

FIG. 6 depicts a block diagram of components of a server and a clientdevice of FIG. 1, in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION

Embodiments of the present invention recognize that a tree datastructure is not designed for easy human consumption on the face of thetree data structure. Embodiments recognize that searching forinformation stored in nodes can be time consuming, as expanding nodes ina tree data structure can lead to many fruitless expansions andcontractions. Embodiments of the present invention also recognize thatusers may have preferences when viewing tree data structures from asimilar source.

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment, generally designated 100, in accordance with oneembodiment of the present invention. FIG. 1 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be madeby those skilled in the art without departing from the scope of theinvention as recited by the claims.

Distributed data processing environment 100 includes server 102 andclient device 104, interconnected over network 112. Network 112represents, for example, a telecommunications network, a local areanetwork (LAN), a wide area network (WAN), such as the Internet, or acombination of the three, and includes wired, wireless, and/or fiberoptic connections. Network 112 includes one or more wired and/orwireless networks that are capable of receiving and transmitting data,voice, and/or video signals, including multimedia signals that includevoice, data, and video information.

In the depicted environment, server 102 is one or more of a managementserver, a web server, or any other electronic device or computing systemcapable of receiving, analyzing, and sending data. In this embodiment,server 102 hosts tree program 120, which augments tree data structures.In other embodiments, server 102 represents a server computing systemutilizing multiple computers as a server system, such as in a cloudcomputing environment. In another embodiment, server 102 represents alaptop computer, a tablet computer, a netbook computer, a personalcomputer (PC), a desktop computer, a personal digital assistant (PDA), asmart phone, or any programmable electronic device capable ofcommunicating with network 112. In another embodiment, server 102represents a computing system utilizing clustered computers andcomponents to act as a single pool of seamless resources. Server 102 mayinclude components, as depicted and described in further detail withrespect to FIG. 6, in accordance with embodiments of the presentinvention. Server 102 includes tree program 120 and database 140.

In depicted distributed data processing environment 100, tree program120 resides on server 102 and augments tree data structures. In variousembodiments, tree program 120 may be accessed by a client device (e.g.,client device 104) or a plurality of client devices (not depicted) vianetwork 112. In some embodiments, tree program 120 may reside on aclient device and operate as an independent standalone program. In anembodiment, tree program 120 may receive files containing tree datastructures to augment (e.g., from client devices). In anotherembodiment, tree program 120 may access a database (e.g., database 140)containing tree data structures, and augment the tree data structurescontained in the database. In various embodiments, tree program 120augments tree data structures based upon preset rules to enable easierreadability for a user. Tree program 120 is depicted and described infurther detail with respect to FIG. 2.

In the depicted embodiment, database 140 resides on server 102. Inanother embodiment, database 140 may reside elsewhere in distributeddata processing environment 100, such as within one or more additionalserver(s) (not shown), within one or more additional client devices(e.g., client device 104), or independently as a standalone databasethat is capable of communicating with tree program 120 via network 112.A database is an organized collection of data. Database 140 isimplemented with any type of storage device capable of storing data thatis accessed and utilized by server 102, such as a database server, ahard disk drive, or a flash memory. In other embodiments, database 140represents multiple storage devices within server 102. Database 140stores information, such as data formats, rules based upon data formats,rules based upon file types, files to augment, etc. In an example,database 140 stores rules stored by a user of tree program 120 dictatingpreferences for displaying nodes related to phone numbers. Database 140includes source file 142.

In the depicted embodiment, source file 142 resides in database 140.Source file 142 is a source of output (e.g., a mobile device) in aspecific data format (e.g., JavaScript™ Object Notation (JSON)), whichhas been stored in database 140. In some embodiments, source file 142may contain a data tree structure. In other embodiments, source file 142may contain source code. In some embodiments, source file 142 isreceived directly by tree program 120 from a client device (e.g., clientdevice 104).

In the depicted embodiment, client device 104 is one or more of adesktop computer, a laptop computer, a tablet computer, a specializedcomputer server, a smart phone, or any programmable electronic devicecapable of communicating with server 102 via network 112 and withvarious components and devices within distributed data processingenvironment 100. In general, client device 104 represents anyprogrammable electronic device or combination of programmable electronicdevices capable of executing machine readable program instructions andcommunicating with other computing devices via a network, such asnetwork 112. Client device 104 may include components as depicted anddescribed in further detail with respect to FIG. 6, in accordance withembodiments of the present invention.

FIG. 2 is a flowchart depicting operational steps of program 200, whichis a function of tree program 120, in accordance with an embodiment ofthe present invention. Program 200 operates on server 102 and augmentstree data structures. In various embodiments, program 200 may create atree data structure from a received or stored file created by a sourceoutput. In one embodiment, an administrator initiates the operationalsteps of program 200 to review tree data structures. In anotherembodiment, tree program 120 may initiate the operational steps ofprogram 200 in response to receiving or storing a new file. In yetanother embodiment, the operational steps of program 200 may initiate atpreset time intervals.

Program 200 stores rules (step 202). In various embodiments, program 200may store rules for user preferences of a tree data structure. Rules arealso known as commands or rule sets. For example, a user may prefer todisplay a node in a tree data structure containing an address which isdisplayed in a specific color and therefore select a color from a listof preset colors to display addresses. In this example, features may beselected in a tree data structure for program 200 to enact a rule, suchas displaying an address. In another example, a user may prefer amultitude of preset rules, such as displaying a node name, filteringnodes, expand expanding nodes, coloring nodes, etc., in the tree datastructure. In this example, the user may select a specific node, such asphone number, address, age, etc., to enact the preset rules. In yetanother example, a user may prefer a combination of preset rules basedon the type of data source of the file, such as a mobile device, alaptop, etc. In some embodiments, program 200 includes a plurality ofuser accounts. Program 200 may store different rule sets for each of theplurality of user accounts, as well as multiple setting for rule setswithin an account.

In various embodiments, program 200 may set rules based upon variousfeatures of a file. In an example of a tree data structure from a mobiledevice (e.g., client device 104), program 200 may set rules based uponthe path of an element, the path length of an element, the root, nodes,child and parent nodes, regular expressions, and/or the differencebetween child node paths.

In some embodiments, program 200 stores preset rules, also referred toas schema, based upon the data source. In an embodiment, program 200 maycreate rules for a file based on data source of the file. In an example,a user or administrator of program 200 creates or selects rules fordisplaying a tree data structure for a file with an email data source.In this example, program 200 utilizes the same rule set for all similardata sources, such as email. In some embodiments, program 200 may storepreset rules based upon the creator of the file and not the data source.For example, program 200 may have preset rules for the display of a treedata structure which may include all files received from a specificlocation, or a specific person, instead of the specific data sourcedevice.

Program 200 receives a file (step 204). In various embodiments, program200 receives a file (e.g., source file 142) from a client device (e.g.,client device 104). In an example, program 200 may receive a filecontaining the tree data structure depicted in FIG. 3 or FIG. 4. Inother embodiments, program 200 may search a database to identify a file(e.g., source file 142). In some embodiments, program 200 may receivemultiple files and store the files in a database, such as database 140.At a later time, program 200 may retrieve one of the stored files fromthe database. In one embodiment, program 200 receives a file that isalready in a tree data structure format. In another embodiment, program200 receives a file that is not in a tree data structure format. Inthese embodiments, program 200 may send the file to a program thatcreates a tree data structure that corresponds to the file and thensends the created tree data structure back to program 200. In someembodiments, program 200 identifies a file which is in a data treestructure based upon the format of the file. In other embodiments, auser may indicate that the file is a data tree structure. In yet otherembodiments, program 200 may determine that a file is a data treestructure by identifying features within the file, such as objects,arrays, nodes, etc.

Program 200 identifies features of a tree data structure (step 206). Insome embodiments, program 200 may receive a file that is already in theformat of a file tree data structure. In these embodiments, program 200may then determine the data format of the file tree data structure.Program 200 determines which of the multiple data formats the file treedata structure originates from and then identifies features of the filetree data structure for the determined specific data format. In anexample, program 200 may receive files that are created in differentdata formats, and program 200 determines the type of data format, whichenables program 200 to identify features in the tree data structure asdifferent formats may have different structures. In some embodiments,program 200 identifies features of a file tree data structure withoutfirst determining the data format. In one example, program 200 onlyreceives files in one type of data format, and therefore, onlyidentifies features of tree data structures for the one data format. Insome embodiments, program 200 receives a file that does not contain afile tree data structure, and program 200 identifies features whichcomprise a file tree data structure contained within the received file.

In various embodiments, program 200 identifies features in the receivedfile, which may comprise a tree data structure. In an example, program200 receives a file that is already in tree data format. Program 200identifies the features of the tree data format based on one or more of:the path of an element, the path length of an element, the root, nodes,child and parent nodes, regular expressions, difference between childnode paths, composition of child node paths specified using relativepaths, object, array, object property, and primitive. In anotherexample, program 200 may receive a file from a data source, such asclient device 104, and send the file to a tree data format program tocreate an initial tree data structure. Program 200 may then receive thefile in tree data form and identify features in the received file whichcomprise the tree data structure.

In some embodiments, program 200 identifies features of a tree datastructure that include specific criteria. Specific criteria may include:does the node path match a regular expression; does a given child pathmap to a value of a given type; does a given child path map to a valuethat evaluates to a given value; does a given child path exist; does agiven child path not map to a value of a given type; does a given childpath not map to a value that evaluates to a given value; does a givenchild path not exist.

Program 200 determines features that match rules (step 208). In someembodiments, program 200 compares the identified features (from step206) to features in the stored rules (from step 202) and determines ifthe features match that will initiate execution of the stored rules. Inan example, program 200 identified a node with a path of“session[0].messages[5].layout.controls[0].currState.text.” Program 200determines if any preset rules match the path for the identified node.In some embodiments, program 200 searches each identified feature (fromstep 206) in the file to determine if are any matches in the storedrules that exist. In other embodiments, program 200 may identify therules for an account and search the received file for matches thatinitiate execution of the rules. In an embodiment, program 200 searchesfor matches of the identified features in step 206 and the rule features(from step 202) one at a time.

Program 200 augments the tree data structure based on the determinedmatches (step 210). In various embodiments, program 200 augments thetree data structure based upon the features that match the presetcommands. In an example, program 200 determines that a match existsbetween a node path and a preset rule for such a node path. Program 200augments the nodes based upon the matched rules. Examples of augmentinga tree data structure based upon matches between identified features andrules include: naming the node using a value of a child node specifiedwith a relative path; naming the node with a static text value; givingthe node a specified color; expanding the node; excluding the node;prefix a name value with some static text; adding static text after aname value; and when expanding a node, also expanding parent nodes upsome number of levels. In various embodiments, after program 200augments a tree data structure, program 200 may send the augmented treedata structure to a client device (e.g., client device 104). In anotherembodiment, program 200 may create a file containing the augmented treedata structure that can be stored in a database (e.g., database 140).

In some embodiments, program 200 may display the augmented tree datastructure when program 200 completes step 210. In other embodiments,program 200 may store a tree data structure in a database (e.g.,database 140) upon the completion of step 210. In yet other embodiments,program 200 may send a file containing an augmented data tree structureto a client device (e.g., client device 104).

In an example, FIG. 5 depicts augmentation to a tree data structurebased upon determined matches. In this example, program 200 identified amatch of the feature “address” in the received file as well as in thestored rules. In response to the determined match for “address”, program200 augments the node to display the street address, the city, thestate, and the postal code without expanding the node.

FIG. 3 depicts an expanded tree data structure. FIG. 3 is arepresentation of a tree data structure that may be received by treeprogram 120. FIG. 3 displays varies nodes which have been expanded todisplay contents of the expanded nodes. In some examples, an expandedtree data structure may consume multiple pages of information and bedifficult for a human to digest.

FIG. 4 depicts a collapsed tree data structure. FIG. 4 is arepresentation of a tree data structure that may be received by treeprogram 120. FIG. 4 depicts the tree data structure from FIG. 3 that hasbeen fully collapsed. FIG. 4 displays varies nodes which have beencollapsed. In some examples, a collapsed tree data structure may bebeneficial to conserve space, but the collapsed tree data structure maynot display information which is useful.

FIG. 5 depicts a collapsed tree data structure that has been augmentedto display certain features while in a collapsed state. FIG. 5 depictsthe tree data structures from FIGS. 3 and 4 that the tree programaugmented. FIG. 5 displays information contained in nodes, which beforeaugmentation are only displayed after a node has been expanded. Examplesof information contained in nodes which have been displayed while thetree data structure is still collapsed in FIG. 5 include: address 21 2ndStreet New York N.Y. 10021, home 212 555-1234, fax 646 555-4567, gendermale.

FIG. 6 depicts a block diagram of components of computer 600, which isrepresentative of server 102 and client device 104, in accordance withan illustrative embodiment of the present invention. It should beappreciated that FIG. 6 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Computer 600 includes communications fabric 602, which providescommunications between computer processor(s) 604, memory 606, persistentstorage 608, communications unit 610, and input/output (I/O)interface(s) 612. Communications fabric 602 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as microprocessors, communications, and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric602 can be implemented with one or more buses.

Memory 606 and persistent storage 608 are computer readable storagemedia. In this embodiment, memory 606 includes random access memory(RAM) 614 and cache memory 616. In general, memory 606 can include anysuitable volatile or non-volatile computer readable storage media.Software and data 622 are stored in persistent storage 608 for accessand/or execution by processor(s) 604 via one or more memories of memory606. With respect to server 102, software and data 622 represents treeprogram 120 and database 140.

In this embodiment, persistent storage 608 includes a magnetic hard diskdrive. Alternatively, or in addition to a magnetic hard disk drive,persistent storage 608 can include a solid-state hard drive, asemiconductor storage device, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), a flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 608 may also be removable. Forexample, a removable hard drive may be used for persistent storage 608.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage608.

Communications unit 610, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 610 includes one or more network interface cards.Communications unit 610 may provide communications through the use ofeither or both physical and wireless communications links. Software anddata 622 may be downloaded to persistent storage 608 throughcommunications unit 610.

I/O interface(s) 612 allows for input and output of data with otherdevices that may be connected to computer 600. For example, I/Ointerface(s) 612 may provide a connection to external device(s) 618,such as a keyboard, a keypad, a touch screen, and/or some other suitableinput device. External device(s) 618 can also include portable computerreadable storage media, such as, for example, thumb drives, portableoptical or magnetic disks, and memory cards. Software and data 622 canbe stored on such portable computer readable storage media and can beloaded onto persistent storage 608 via I/O interface(s) 612. I/Ointerface(s) 612 also connect to a display 620.

Display 620 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method for augmenting data tree structures, the method comprising: identifying, by one or more computer processors, a tree data structure; identifying, by one or more computer processors, one or more features in the identified tree data structure, wherein the one or more features comprise at least one of: a node of the tree data structure, an object of the tree data structure, an array of the tree data structure, an object property of the tree data structure, and a root of the tree data structure, wherein identifying one or more features of the identified tree data structure comprises: identifying, by one or more computer processors, a path of a node in the tree data structure that matches a regular expression; determining, by one or more computer processors, whether one of the one or more identified features matches a feature that initiates execution of a rule, wherein the rule defines augmentations to the tree data structure based upon one or more features in the tree data structure, wherein a feature that initiates execution of a rule comprises one of: determining, by one or more computer processors, that a node path matches a regular expression, determining, by one or more computer processors, that a child node path maps to a preset value, determining, by one or more computer processors, that a child node path maps to a value that evaluates to a preset value, and determining, by one or more computer processors, that a child node path exists; and identifying, by one or more computer processors, a child node in the tree data structure and determining, by one or more computer processors, if one or more features of the child node of the tree data structure match a feature that initiates execution of a rule, wherein features of the child node comprise at least one of: a type of the child node, a value of the child node, and an existence of the child node; and in response to determining that one or more identified features match at feature that initiates execution of a rule, augmenting, by one or more computer processors, the identified tree data structure based upon the determined one or more matches of the one or more identified features and the feature that initiates execution of the rule, wherein augmenting the identified data tree structure further comprises: identifying, by one or more computer processors, a first feature of the one or more identified features determined to match the feature that initiates execution of the rule; and augmenting, by one or more computer processors, the identified first feature of the one or more identified features, wherein augmenting comprises one or more of: naming a node of the tree data structure, coloring a node of the tree data structure, expanding a node of the tree data structure, excluding a node from a tree data structure, adding static text before a name in the tree data structure, adding static text after a name in the tree data structure, adding text both before and after a name in the tree data structure, expanding a parent node of the node in the tree data structure based on a feature of the node. 